Beginner's Tutorial: Tencent Cloud Korea VPS Rapid Website Setup And Performance Testing Methods

First, select "Cloud Server / Lightweight Application Server" on the Tencent Cloud console, and switch the region to South Korea (Seoul) or the corresponding node (usually ap-seoul). Beginners are advised to choose a "lightweight application server" or entry-level CVM, starting with 1-2 cores, 1-2GB memory, and 50GB SSD, with bandwidth of 1-5Mbps depending on traffic volume. For images, it is recommended to choose a stable system, such as Ubuntu 22.04 LTS or Debian. If you need Windows, choose the corresponding image.

Billing options include monthly subscription or pay-as-you-go (pay-as-you-go is recommended during the testing phase). If you want to deploy quickly on the image, you can use the "Application Image"—including LNMP/LAMP/Baota panels, etc.—to reduce manual configuration time. Confirm that the default rules for security groups/firewalls allow ports 22 (SSH)/80/443.

Choosing a Korean node is for lower latency access to Korean users, but if the target user is in Chinese mainland, cross-border access speed and filing issues need to be evaluated (Chinese mainland access to overseas nodes may be affected by latency and bandwidth).

After purchase, use the Elastic Public IP (EIP) provided by the console and log in via SSH (e.g., ssh root@IP). If logging in with a key, save the private key in advance and set appropriate permissions (chmod 600).

Below are the quick deployment steps for Ubuntu, suitable for beginners to get started quickly: update the system -> install Nginx, MySQL, PHP -> configure sites -> configure SSL.

Update the system: apt update & apt upgrade -y. Install Nginx: apt install nginx -y; Install MySQL: apt install mysql-server -y (run mysql_secure_installation for the first time). Install PHP and extensions: apt install php-fpm php-mysql -y. Start and set boot auto-start: systemctl enable --now nginx php7.4-fpm MySQL.

Create a site directory in /var/www/yourdomain, set owner to www-data:chown -R www-data:www-data /var/www/yourdomain. Create the Nginx site configuration pointing to php-fpm socket, test the configuration with nginx -t, and overload systemctl to reload nginx.

Install certbot: apt install certbot python3-certbot-nginx -y, run certbot --nginx -d yourdomain.com to automatically request and enable HTTPS in the Nginx configuration.

Domain A records point to public IP of the Korean VPS, and once DNS resolution is effective, you can access it directly. To improve global access speed and reliability, it is recommended to connect with a CDN (such as Tencent Cloud CDN, Cloudflare, etc.) and configure the CDN console as the source server as VPS IP or CNAME.

Set the A record and maintain an appropriate TTL (short TTL can be set during testing to facilitate switching). If using a CDN, the domain name is usually resolved to the CNAME provided by the CDN, and then the origin information is configured in the CDN console.

After enabling the CDN, set caching rules (static long cache, HTML short cache or no cache), and configure certificates on the CDN (many CDNs support automatic certificate hosting or use built-in certificates). At the same time, mandatory HTTPS and HSTS configurations are made on the origin site (use with caution as needed).

If target users are distributed across multiple regions, it is recommended to deploy or use multi-regional origin + intelligent routing CDN at multiple nearest nodes; For Chinese mainland users, consider filing or using Hong Kong/mainland nodes to reduce access issues.

Security is a long-term task, with basic measures including closing unnecessary ports, enabling firewalls, limiting SSH logins, and regularly updating and backing up. It is recommended to use ufw or security group policies to open only necessary ports (22/80/443), and change the SSH port, disable root password login, or log in with a key.

Regularly back up database and website files, and it is recommended to use automated scripts, cloud drives, or object storage (COS) snapshots. Configure monitoring alerts (CPU/memory/disk/network); Tencent Cloud provides cloud monitoring or uses Prometheus+Grafana.

Install Fail2ban brute-force protection, use HTTPS and automatically renew certificates (certbot renew), limit PHP upload size, and enable necessary SELinux/AppArmor rules (if applicable).

Retain system images or snapshots, allowing quick rollback in case of failure; Use regular full + incremental backups for the database and test recovery processes to ensure backups are available.

Performance testing is divided into three categories: network layer, server resources, and page loading. Common commands: ping -c 4 yourdomain, traceroute yourdomain, mtr yourdomain are used to detect network latency and routing; curl -I -w '%{time_starttransfer}' -o /dev/null yourdomain Used to measure TTFB.

ab (ApacheBench): ab -n 1000 -c 50 http://yourdomain/ for simple concurrency testing; Siege, WRK, and K6 offer richer scripted stress tests. Be sure to inform the bandwidth and its impact before pressure testing to avoid irreversible effects on production.

htop/top checks CPU memory, iostat or vmstat checks disk, ss/netstat checks connection count. For PHP-FPM/Nginx, check the slow request logs, adjust worker_connections, worker_processes, and parameters like pm.max_children in PHP-FPM.

Analyze page loading bottlenecks using WebPageTest, GTmetrix, and Google PageSpeed Insights: compressing images, enabling Gzip/Brotli, using CDNs, setting cache headers, merging/delaying JS and CSS loading, optimizing database queries, and enabling object caching (Redis).